Skip to content

test(pipeline7): reproduce srj24 sample 4 topology gap - #1798

Draft
ShiboSoftwareDev wants to merge 1 commit into
mainfrom
agent/repro-srj24-sample4-topology
Draft

test(pipeline7): reproduce srj24 sample 4 topology gap#1798
ShiboSoftwareDev wants to merge 1 commit into
mainfrom
agent/repro-srj24-sample4-topology

Conversation

@ShiboSoftwareDev

@ShiboSoftwareDev ShiboSoftwareDev commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

What this reproduces

This adds a reduced srj24 sample 4 fixture for the topology failure that occurs before port-point pathing:

  1. a regular BGA pad grid is embedded in a larger mixed-pad component;
  2. whole-component BGA detection rejects that component;
  3. the top and bottom terminals therefore have no legal cross-layer capacity path.

The test intentionally asserts the failing behavior and contains no production-code changes.

Step visualization

srj24 sample 4 topology reproduction

The four frames show the mixed package, its hidden regular core, the isolated terminal layers, and the missing cross-layer edge.

Verification

  • bun test tests/features/topology/srj24-sample4-topology-repro.test.ts --timeout 9999999
  • bun run build

@vercel

vercel Bot commented Jul 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
capacity-node-autorouter Ready Ready Preview Jul 31, 2026 5:20am

Request Review

@tscircuitbot

Copy link
Copy Markdown
Contributor

Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [benchmark.sh args...]
/benchmark-long [benchmark.sh args...]
/benchmark-all

Comment /benchmark to run the default dataset, or append any arguments accepted by ./benchmark.sh.
Comment /benchmark-long for an 8-vCPU run that defaults to 8 workers and has an eight-hour timeout.
Comment exactly /benchmark-all to start separate workflow runs and result comments for the default dataset plus srj18, srj19, srj20, srj21, and srj23.

Everything after /benchmark or /benchmark-long is safely forwarded to ./benchmark.sh, except --profile-solvers, which enables profile comparison tables.
Examples: /benchmark --dataset 18 --sample-timeout 2000s, /benchmark --pipeline 7 --scenario-limit 20, /benchmark all 20 --concurrency 8, and /benchmark-long --dataset 18.

Use /update-snapshots (or /us) to run BUN_UPDATE_SNAPSHOTS=1 bun test --timeout 120_000 on the PR branch and auto-commit snapshot updates.
Use /usf to read recent failed test files, update and verify their exact CI test shards, and auto-commit only their snapshots. It uses the configured fast benchmark runner by default; use /usf --ubuntu-latest for GitHub-hosted x64 CI parity.

Any PR whose title contains [BENCHMARK TEST] will automatically run one default-dataset benchmark on PR updates; it does not post a PR result comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants